New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes to the nodes info API #4055
Labels
Comments
ghost
assigned spinscale
Dec 3, 2013
After reading #4057 - why not simply make the URL |
I'd be up for supporting |
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 11, 2014
…` to `/_nodes` The "_cluster" prefix has been removed in Elasticsearch 1.0. The "/_nodes" endpoint is supported since ~ version 0.19, so this doesn't break backwards compatibility. Related: * elastic/elasticsearch#4055 * elastic/elasticsearch#4065 * elastic/elasticsearch#4347 * elastic/elasticsearch#4608
brusic
pushed a commit
to brusic/elasticsearch
that referenced
this issue
Jan 19, 2014
Important: This breaks backwards compatibility with 0.90 * Removed endpoints: /_cluster/nodes, /_cluster/nodes/nodeId1,nodeId2 * Disallow usage of parameters, but make required metrics part of URI * Changed NodesInfoRequest to return everything by default * Fixed NPE in NodesInfoResponse Closes elastic#4055
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 23, 2014
Due to changes in Elasticsearch 1.0 API, the client "namespaces" have been changed to reflect the change in URLs: `_cluster/nodes` => `_nodes` Thus, instead of: client.cluster.nodes_info the new API is: client.nodes.info Related: * elastic/elasticsearch#4055 * elastic/elasticsearch#4336 * elastic/elasticsearch#4769
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 24, 2014
Due to changes in Elasticsearch 1.0 API, the client "namespaces" have been changed to reflect the change in URLs: `_cluster/nodes` => `_nodes` Thus, instead of: client.cluster.nodes_info the new API is: client.nodes.info Related: * elastic/elasticsearch#4055 * elastic/elasticsearch#4336 * elastic/elasticsearch#4769
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 24, 2014
Due to changes in Elasticsearch 1.0 API, the client "namespaces" have been changed to reflect the change in URLs: `_cluster/nodes` => `_nodes` Thus, instead of: client.cluster.nodes_info the new API is: client.nodes.info Related: * elastic/elasticsearch#4055 * elastic/elasticsearch#4336 * elastic/elasticsearch#4769
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 28, 2014
Due to changes in Elasticsearch 1.0 API, the client "namespaces" have been changed to reflect the change in URLs: `_cluster/nodes` => `_nodes` Thus, instead of: client.cluster.nodes_info the new API is: client.nodes.info Related: * elastic/elasticsearch#4055 * elastic/elasticsearch#4336 * elastic/elasticsearch#4769
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 29, 2014
Due to changes in Elasticsearch 1.0 API, the client "namespaces" have been changed to reflect the change in URLs: `_cluster/nodes` => `_nodes` Thus, instead of: client.cluster.nodes_info the new API is: client.nodes.info Related: * elastic/elasticsearch#4055 * elastic/elasticsearch#4336 * elastic/elasticsearch#4769
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 29, 2014
Due to changes in Elasticsearch 1.0 API, the client "namespaces" have been changed to reflect the change in URLs: `_cluster/nodes` => `_nodes` Thus, instead of: client.cluster.nodes_info the new API is: client.nodes.info Related: * elastic/elasticsearch#4055 * elastic/elasticsearch#4336 * elastic/elasticsearch#4769
javanna
added a commit
that referenced
this issue
Feb 6, 2014
javanna
added a commit
that referenced
this issue
Feb 6, 2014
javanna
added a commit
that referenced
this issue
Feb 6, 2014
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recommendations:
Remove the
all
andclear
flags. Default to returnall
by default, unless specific metrics specified.Change the path format to:
where:
{nodes}
: comma-delimited list of nodes or blank{metric}
is blank or comma-delimited list of metricsMetrics can be any of:
NOTE: Node names and metric names could clash, if you name your nodes eg
process
. Should probably accept_all
in the{nodes}
parameter.The text was updated successfully, but these errors were encountered: